Current code is mostly POC and getting familiar with contacts code base.

Questions:

• after pressing send button on the invitation form the ContactDetails.editMode property should be set to false to display the contact (same behavior as pressing the contact save button). How do we do that?
  Would a custom PropertyCloudId component to be used instead of ContactDetailsProperty for the cloud ID field make sense?
  Or should we simply forward/bind the editMode flag to the ContactDetailsProperty --> PropertyText --> CloudIdExchangeInvite component chain.
  Use a dedicated PropertyCloudId component (based on PropertyText with additional 'invite', 'accept', 'decline', 'revoke' buttons).
• After closing the send invitation form (click 'Send') and setting the ContactDetails edit mode to false the email is not immediately show, how's that?

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

Codecov Report

Attention: Patch coverage is 0% with 139 lines in your changes missing coverage. Please review.

Project coverage is 2.22%. Comparing base (0714ac0) to head (e7c2604).
Report is 18 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (0714ac0) and HEAD (e7c2604). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (0714ac0)	HEAD (e7c2604)
	2	1

@@             Coverage Diff             @@
##               main   #4417      +/-   ##
===========================================
- Coverage     11.03%   2.22%   -8.82%     
===========================================
  Files           122      99      -23     
  Lines          5589    4989     -600     
  Branches       1209    1261      +52     
===========================================
- Hits            617     111     -506     
+ Misses         4850    4756      -94     
  Partials        122     122              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Thanks for the contribution, @redblom!

The features relies on an implementation of the Invitation Workflow (see https://github.com/sara-nl/nc-collaboration).

Is there any way this could work without introducing an app dependency?

Thanks for the contribution, @redblom!

The features relies on an implementation of the Invitation Workflow (see https://github.com/sara-nl/nc-collaboration).

Is there any way this could work without introducing an app dependency?

Short answer: No, that is to say, the actual cloud ID exchange is not a responsibility of the contacts app but the contacts app (the cloud ID field) is a logical place where to have this option (as per earlier discussion with the Design Team).
The feature actually depends on the implementation of OCM /invite-accepted. This is currently in the process of being implemented for nextcloud server core (nextcloud/server#51113) so cloud ID exchange can become an integral part of nextcloud. Up until then there should be an app present implementing this.
The idea is to make the option not visible to the user when the platform can not do the actual cloud ID exchange (by configuration).
(so the best answer is: yes, when cloud ID exchange has become an integral part of nextcloud :)

Thanks for the clarification